Bump Testcontainers and Testcontainers.MariaDb #1124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated Testcontainers from 4.7.0 to 4.8.0.
Release notes
Sourced from Testcontainers's releases.
4.8.0
What's Changed
Thank you to all the contributors 🙌.
In version
4.7.0
, we noticed that the reuse hash could change depending on the order of dictionary values. This has been fixed to ensure that dictionary values are processed in a consistent order when generating the reuse hash. As a result, the reuse hash will likely change again with4.8.0
.Wait strategies now default to the
Running
mode. This mode expects the container to remain running throughout startup. If the container exits unexpectedly, Testcontainers will throw aContainerNotRunningException
that includes the exit code and container logs.The container startup callback now includes an additional overload that provides the actual container configuration. If you implement
IContainerBuilder<TBuilderEntity, TContainerEntity>
, you need to add the container configuration (e.g.,IContainerConfiguration
) as a third generic type constraint toIContainerBuilder
.IContainerBuilder.WithResourceMapping
andIContainer.CopyAsync
now include two new optional arguments:uid
andgid
. If you do not need to specify those, use named arguments for the existing parameters:fileMode
orct
.🚀 Features
WithTarget(string)
to image builder (#1534) @HofmeisterAn🐛 Bug Fixes
db.runCommand({hello:1})
do detect readiness (#1548) @HofmeisterAn📖 Documentation
IContainerBuilder.WithAutoRemove
code comment (#1546) @hojmark🧹 Housekeeping
... (truncated)
Commits viewable in compare view.
Updated Testcontainers.MariaDb from 4.7.0 to 4.8.0.
Release notes
Sourced from Testcontainers.MariaDb's releases.
4.8.0
What's Changed
Thank you to all the contributors 🙌.
In version
4.7.0
, we noticed that the reuse hash could change depending on the order of dictionary values. This has been fixed to ensure that dictionary values are processed in a consistent order when generating the reuse hash. As a result, the reuse hash will likely change again with4.8.0
.Wait strategies now default to the
Running
mode. This mode expects the container to remain running throughout startup. If the container exits unexpectedly, Testcontainers will throw aContainerNotRunningException
that includes the exit code and container logs.The container startup callback now includes an additional overload that provides the actual container configuration. If you implement
IContainerBuilder<TBuilderEntity, TContainerEntity>
, you need to add the container configuration (e.g.,IContainerConfiguration
) as a third generic type constraint toIContainerBuilder
.IContainerBuilder.WithResourceMapping
andIContainer.CopyAsync
now include two new optional arguments:uid
andgid
. If you do not need to specify those, use named arguments for the existing parameters:fileMode
orct
.🚀 Features
WithTarget(string)
to image builder (#1534) @HofmeisterAn🐛 Bug Fixes
db.runCommand({hello:1})
do detect readiness (#1548) @HofmeisterAn📖 Documentation
IContainerBuilder.WithAutoRemove
code comment (#1546) @hojmark🧹 Housekeeping
... (truncated)
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)